Add FAIL_ON_UNCOVERED_LINES input to fail on coverage gaps - #44
Merged
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
martin4861
changed the title
FAIL_ON_UNCOVERED_LINES input to fail on coverage gaps
martin4861
marked this pull request as ready for review
July 31, 2026 13:40
ggilder
approved these changes
Aug 1, 2026
ggilder
left a comment
ggilder
left a comment
Owner
There was a problem hiding this comment.
This is great! Thank you for the contribution.
Owner
|
Published as v1.4.0 / updated v1 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an opt-in
FAIL_ON_UNCOVERED_LINESinput. When enabled and at least one annotation is produced, theAnnotatecheck run finishes withconclusion: 'failure'and the step fails viacore.setFailed(). This lets a repo block PRs that introduce coverage gaps.Default is
false, so existing consumers are unaffected.annotate()now takes an optionalconclusion(defaults tosuccess); the inline conclusion union is extracted into an exportedCheckConclusiontype.annotation_levelchanges tofailureTesting
npm run allpasses. Added tests forannotate()covering the default success conclusion, a forwarded failure conclusion, conclusion only being set on the final chunk for >50 annotations, and the no-annotations early return.Not enabled in this repo's own
test.yml, since it annotates its own PRs.